This repository has been archived by the owner on May 7, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
B-17159
Summary
Updated
.envrc
with Okta client IDs, secrets, and okta tenant URL (secrets & tenant URL in chamber) for local dev environment that serves:milmovelocal:3000/
officelocal:3000/
adminlocal:3000/
Followed these instructions in Confluence to manage secrets: https://dp3.atlassian.net/wiki/spaces/MT/pages/1249542242/0030+How+to+Manage+Secrets+with+Chamber
Setup to Run the Code
NOTE: if you are getting
AWS_PROFILE: unbound variable
, try runningexport AWS_PROFILE=transcom-gov-dev
make client_run
andmake server_run
in separate terminalsInternal Server Error
due to incomplete session management), but this does verify proper management of secrets and client ids for each MilMove application.How to test
Automated testing is currently on hold until remaining login features are implemented
chamber list app-devlocal
in your terminal to see the listed secrets.chamber read app-devlocal okta-customer-secret-key
chamber read app-devlocal okta-office-secret-key
chamber read app-devlocal okta-admin-secret-key
Backend